Zen

Translation

English type: Plain text
The steps in this part are similar to part 1. However, GNU Hello has more quirks than Banner does, so some workarounds and custom steps are needed. Each package's quirks are unique, so these are best viewed as examples of the kind of problems that may arise when packaging.
0/2750 · 275

Sign in to save the translation.

English French Actions
Packaging Tutorial 2: GNU Hello
 
This tutorial demonstrates RPM packaging by packaging the https://www.gnu.org/software/hello/[GNU Hello] program. While the program itself is simple, it also comes with many peripheral components of a FOSS project: configuration/build/install environment, documentation, internationalization,etc.
 
This tutorial is the second part of Fedora packaging tutorial. It follows the same basic structure as xref:Packaging_Tutorial_1_banner.adoc[part 1]. If you have not completed it yet, please do so before continuing with this tutorial.
 
The steps in this part are similar to part 1. However, GNU Hello has more quirks than Banner does, so some workarounds and custom steps are needed. Each package's quirks are unique, so these are best viewed as examples of the kind of problems that may arise when packaging.
 
Installing Packager Tools
 
Follow xref:Installing_Packager_Tools.adoc[Installing Packager Tools].
 
Creating the package directory
 
For GNU Hello, the package can simply be named `hello`. This is also the name of Fedora's https://packages.fedoraproject.org/pkgs/hello/hello/[official GNU Hello package].
 
$ mkdir hello && cd hello
 
Inside a Spec File
 
Create a file called `hello.spec` and paste the following minimal specfile. This already has `BuildRequires` tags for `gcc` and `make`, since that topic was already covered in part 1. Similarly, `%files` section already includes the resulting binary, man pages, documentation and license file. For GNU Hello, all these files are very similar to corresponding files in Banner, and were thus already covered in part 1.
 
Also, for reasons that are too complex to explain in a tutorial, in some situations `texinfo` package is also needed, and so a `BuildRequires` line is added for it.
 
Name: hello
Version: 2.10
Release: %autorelease
Summary: Produces a familiar, friendly greeting
License: GPL-3.0-or-later
URL: https://www.gnu.org/software/hello/
Source: http://ftp.gnu.org/gnu/hello/hello-%{version}.tar.gz
BuildRequires: gcc
BuildRequires: make
BuildRequires: texinfo
 
%description
The GNU Hello program produces a familiar, friendly greeting. Yes, this is
another implementation of the classic program that prints "Hello, world!" when
you run it.
 
%prep
%autosetup
 
%build
%configure
%make_build
 
%install
%make_install
 
%files
%{_bindir}/hello
%{_mandir}/man1/hello.1.*
%doc AUTHORS ChangeLog NEWS README THANKS TODO
%license COPYING
 
%changelog
%autochangelog
 

Loading…

User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Packaging_Tutorial_2_GNU_Hello
  3. French
The steps in this part are similar to part 1. However, GNU Hello has more quirks than Banner does, so some workarounds and custom steps are needed. Each package's quirks are unique, so these are best viewed as examples of the kind of problems that may arise when packaging.
 
4 weeks ago
Browse all string changes

Glossary

English French
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./@]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?"
Source string location
pages/Packaging_Tutorial_2_GNU_Hello.adoc:21
String age
4 weeks ago
Last updated
4 weeks ago
Source string age
4 weeks ago
Translation file
po/fr/master/pages/Packaging_Tutorial_2_GNU_Hello.po, string 4